fix: unrunnable CLI binary, lock poisoning on failed translation, deletion persistence, locale matching - #3

Fixes six verified bugs in v1.1.0, spanning the CLI binary, lock-file integrity, deletion handling, locale detection, and the ai dependency contract.

1. Unrunnable CLI binary (blocker)

Before: src/cli.ts carried its own #!/usr/bin/env node AND tsup.config.ts added a banner shebang, so dist/cli.js started with two shebang lines — a syntax error under both node and bun. The published 1.1.0 solid-translate binary could not run at all.

After: the source shebang is removed (the tsup banner is the single source of truth), and CI now smoke-tests node dist/cli.js --help and bun dist/cli.js --help after every build so this can never regress.

2. Lock poisoning on failed translation (blocker)

Before: lock entries were recorded for keys before translation ran, and batch failures were caught-and-continued — then target files and the lock were written anyway. A failed run (e.g. missing API key) wrote es.json as {} plus a fully-populated lock; the rerun said "No changes detected". Silent, permanent corruption.

After: the diff produces pending lock entries that are committed only for keys whose batches succeeded for all target locales. Successful batches are still written, but on any failure the CLI exits non-zero naming the failed locales/keys, and the Vite plugin throws (fails the build) with the same detail. The lock never claims a key is translated when it isn't; failed keys are retried on the next run.

3. Deleted keys never persisted

Before: when the only change was deleted source keys, the "no changed keys" early return skipped all writes, so removed strings lived in target locale files (and shipped bundles) forever.

After: a deletions-only run prunes the deleted keys from every target file and writes the updated lock — with zero AI calls.

4. CLI dropped context from lock entries

Before: CLI-written lock entries omitted context while Vite-written ones included it, so mixing solid-translate translate with Vite autoExtract re-translated every context-annotated key on each tool switch.

After: the CLI preserves existing lock contexts when rewriting entries (and passes them as hints to the translator). Bonus: the Vite plugin with autoExtract: false no longer wipes contexts either.

Fixes 2–4 are single-sourced: the previously duplicated (and divergent) lock/diff/write logic in cli.ts and vite.ts now lives in a shared src/lock.ts (diffLock + syncLocaleFiles), used by both entry points.

5. Locale detection case bug

Before: detectLocale lowercased the browser locale but compared against availableLocales verbatim — an available "pt-BR" never matched a browser "pt-br"/"pt-BR" and fell through to the default.

After: matching is case-insensitive and returns the canonical casing from availableLocales ("pt-br" → "pt-BR").

6. Lazy ai import + correct peer range

Before: dist/vite.js statically imported generateObject from ai, so merely loading the Vite plugin required ai installed even for extract-only or fresh-lock builds. The peer range ai >=3.0.0 also admitted ai v5, which removed the LanguageModelV1 type this package uses.

After: every ai import is a lazy await import("ai") executed only when translation actually runs (verified: the plugin loads and completes a fresh-lock buildStart with node_modules/ai removed). Peer range is now ">=3.0.0 <5.0.0".

Tests

• New tests/lock.test.ts: 20 tests covering diffing, lock-poisoning/retry behavior, per-batch and per-locale failure isolation, deletion-only pruning, CLI↔Vite context parity, and corrupted-lock recovery (stubbed translator, real temp-dir fs).
• tests/locale-detect.test.ts: 5 new case-sensitivity/canonical-casing tests.
• Full suite: 63 pass, 0 fail. bun run build, bunx tsc --noEmit, and node+bun smoke of dist/cli.js all green.

No public API changes. src/extract.ts and the virtual-module design are untouched.

🤖 Generated with Claude Code